 $ type SYS$HELP:CDD034.RELEASE_NOTES












               VAX Common Data Dictionary Release Notes


                        Order No. AA-GK49C-TE



                           November 1987




          This manual contains the release notes for VAX Common Data
          Dictionary.






          Operating System:  VMS
                             MicroVMS

          Software Version:  VAX CDD V3.4






        digital equipment corporation, maynard, massachusetts
















The information in this document is subject to change
without notice and should not be construed as a
commitment by Digital Equipment Corporation.  Digital
Equipment Corporation assumes no responsibility for
any errors that may appear in this document.

The software described in this document is furnished
under a license and may be used or copied only in
accordance with the terms of such license.

No responsibility is assumed for the use or
reliability of software on equipment that is not
supplied by DIGITAL or its affiliated companies.


Copyright (c) 1981, 1982, 1983, 1984, 1985, 1986, 1987
by Digital Equipment Corporation.  All rights
reserved.


The postage paid READER'S COMMENTS form on the last
page of this document requests your critical
evaluation to assist us in preparing future
documentation.

The following are trademarks of Digital Equipment
Corporation:


ACMS           DECUS          UNIBUS
CDD            MicroVAX       VAX
DATATRIEVE     MicroVMS       VAXcluster
DEC            PDP            VAX Information
Architecture
DECgraph       Rdb/ELN        VMS
DECnet         Rdb/VMS        VT
DECslide       TDMS













                                   CONTENTS

                Intended Audience  . . . . . . . . . . . . . . . . . v
                Operating System Information . . . . . . . . . . . . v
                Structure  . . . . . . . . . . . . . . . . . . . . . v
                Related Documents  . . . . . . . . . . . . . . . . . v
                References to Products . . . . . . . . . . . . . .  vi


CHAPTER 1       Release Notes

                Problems Corrected in CDD Version 3.4  . . . . . . 1-1
                  Corrected Parsing Error on END RECORD Syntax . . 1-1
                  Corrected Virtual Memory Error During BACKUP, 
                  RESTORE, or COPY . . . . . . . . . . . . . . . . 1-1
                  You Cannot Back Up CDD$TOP . . . . . . . . . . . 1-2
                  Wildcards Work Properly When CDD$TOP Is a 
                  Logical Name . . . . . . . . . . . . . . . . . . 1-2
                  CREATE Command Now Includes a /SUBDICTIONARY 
                  Qualifier  . . . . . . . . . . . . . . . . . . . 1-3
                  Subdictionary File Specifications Can Contain 
                  Any System Logical Name  . . . . . . . . . . . . 1-3
                  You Can Name "Hardwired TXcn" Terminal Type in 
                  the ACL Editor . . . . . . . . . . . . . . . . . 1-3
                Support of the VAX Language-Sensitive Editor (LSE) 1-3
                /DIAGNOSTICS Qualifier for CDDL Command  . . . . . 1-4
                DECreporter Support  . . . . . . . . . . . . . . . 1-5
                CDDL Alternative File Extension in CDD Version 3.3 
                and Later  . . . . . . . . . . . . . . . . . . . . 1-5
                CDD Version 3.4 and VAX/VMS Version 4.4  . . . . . 1-6
                Installing CDD on a Cluster  . . . . . . . . . . . 1-6
                Underscore Preceding CDD_$TOP  . . . . . . . . . . 1-7
                Using Multiple Versions of CDD Objects with 
                DATATRIEVE . . . . . . . . . . . . . . . . . . . . 1-7
                Installing CDD with SYSPRV . . . . . . . . . . . . 1-7
                Path Names Pointing to Subdictionary Files . . . . 1-8
                The CDDL ALIGNED Clause  . . . . . . . . . . . . . 1-8
                DMU Restrictions . . . . . . . . . . . . . . . . . 1-9
                  Copying and Renaming a Dictionary Object 
                  Protected by a Password  . . . . . . . . . . . . 1-9


                                 iii





                  Using /STAGE with DMU RESTORE  . . . . . . . . . 1-9
                  Using a Wildcard with the DELETE/SUBDICTIONARY 
                  Command  . . . . . . . . . . . . . . . . . . .  1-10

















































                                  iv


























                                           How to Use This Manual

                                           How to Use This Manual


This manual provides information about the Version 3.4 of VAX
Common Data Dictionary (CDD) software, also referred to in this
                                                  ___ ______ ____

book as CDD.  This manual replaces Version 3.4 of VAX Common Data
__________ _______ _____

Dictionary Release Notes



Intended Audience

Intended Audience

This manual contains information not included in other manuals
for data administrators, system managers, programming
supervisors, and programmers.



Operating System Information

Operating System Information

Information about the versions of the operating system and
related software that are compatible with this version of CDD is
included in the CDD media kit, in either the Installation Guide
or the Before You Install letter.

Contact your DIGITAL representative if you have questions about
the compatibility of other software products with this version of
                                                  ___ ______

CDD.  You can request the most recent copy of the VAX System
________ _____ ______________ ________ _____ _________ _____

Software Order Table/Optional Software Cross Reference Table, SPD
28.98.xx, which will verify which versions of your operating
system are compatible with this version of CDD.



Structure

Structure

This manual consists of a single chapter of release notes.



Related Documents

Related Documents

For further information on CDD, you can refer to:

   ___ ______ ____ __________ ______ _____

o  VAX Common Data Dictionary User's Guide

   Describes how to use the CDD and its three utilities:  DMU,
   CDDV, and CDDL.  This task-oriented guide contains information
   useful to the data administrator or system manager about
   designing, creating, protecting, and maintaining the CDD.


                                  v


























   ___ ______ ____ __________ _________ _________ ______

o  VAX Common Data Dictionary Utilities Reference Manual

   Explains how to use the Dictionary Management Utility (DMU)
   and the Dictionary Verify/Fix Utility (CDDV).

   ___ ______ ____ __________ ____ __________ ________ _________

o  VAX Common Data Dictionary Data Definition Language Reference
   ______

   Manual

   Provides a complete description of the CDD Data Definition
   Language Utility (CDDL).  This manual also contains
   information about CDDL compatibility with VAX programming
   languages and other VAX Information Architecture components.

   ___ ______ ____ __________ ____________ _____

o  VAX Common Data Dictionary Installation Guide

   Shows how to install the CDD software and run the Installation
   Verification Procedure (IVP).




References to Products

References to Products

CDD is a member of the VAX Information Architecture, a group of
products that work with each other and with VAX languages
conforming to the VAX calling standard to provide flexible
solutions for information management problems.

VAX Information Architecture documentation explaining how these
products interrelate is included with VAX CDD documentation.  VAX
Information Architecture documentation is also available
separately.  Contact your DIGITAL representative.

The CDD documentation to which this manual belongs often refers
to products that are part of the VAX Information Architecture by
their abbreviated names:

o  VAX ACMS software is referred to as ACMS.

o  VAX CDD software is referred to as CDD.

o  VAX DATATRIEVE software is referred to as DATATRIEVE.

o  VAX DBMS software is referred to as DBMS.

o  VAX Rdb/VMS software is referred to as Rdb/VMS.

o  VAX TDMS software is referred to as TDMS.




                                  vi


























o  VIDA software is referred to as VIDA.









































                        vii














                     Chapter 1

                     Chapter 1

                   Release Notes

                   Release Notes



Problems Corrected in CDD Version 3.4

Problems Corrected in CDD Version 3.4

Version 3.4 corrects several bugs in previous
versions of CDD.



Corrected Parsing Error on END RECORD Syntax

Corrected Parsing Error on END RECORD Syntax

In previous versions of CDD, the CDDL compiler would
generate an error message if you supplied a pathname
with the "END RECORD" clause that did not match the
pathname you used with the "DEFINE RECORD clause.
With this release, the problem is corrected.



Corrected Virtual Memory Error During BACKUP,

Corrected Virtual Memory Error During BACKUP,
RESTORE, or COPY

RESTORE, or COPY

In previous versions of CDD, the BACKUP, COPY, or
RESTORE commands could sometimes generate
"Insufficient virtual memory" errors.  With this
release, the problem is corrected.



                        1-1



Release Notes

Release Notes


You Cannot Back Up CDD$TOP

You Cannot Back Up CDD$TOP

In previous versions of CDD, the BACKUP command let
you back up the root directory, CDD$TOP.  However,
the RESTORE command cannot restore a file containing
CDD$TOP.  Therefore, DMU now generates an error
message when you try to back up CDD$TOP.



Wildcards Work Properly When CDD$TOP Is a Logical

Wildcards Work Properly When CDD$TOP Is a Logical
Name

Name

In previous versions of CDD, DMU commands containing
wildcards sometimes fail if CDD$TOP translates to
another pathname.  With this release, the problem is
corrected.

























                        1-2



                                       Release Notes

                                       Release Notes


CREATE Command Now Includes a /SUBDICTIONARY

CREATE Command Now Includes a /SUBDICTIONARY
Qualifier

Qualifier

In previous versions of CDD, the documentation
described a
/NOSUBDICTIONARY qualifier for the CREATE command,
but the qualifier did not work.  With this release,
the problem is corrected.  That is, the
/SUBDICTIONARY qualifier now works as documented.



Subdictionary File Specifications Can Contain Any

Subdictionary File Specifications Can Contain Any
System Logical Name

System Logical Name

In previous versions of CDD, within a dictionary
file specification, you could use only logical names
from the LNM$SYSTEM_TABLE table.  With this release,
you can use a logical name from any system logical
name table defined in LNM$SYSTEM.



You Can Name "Hardwired TXcn" Terminal Type in the

You Can Name "Hardwired TXcn" Terminal Type in the
ACL Editor

ACL Editor

Dictionary Access Control List Entries (ACLs)
include user identification criteria, in which you
indicate a user or class of users to which the entry
applies.  Previous versions of CDD prevented you
from naming a hardwired terminal of class TXcn in
the user identification criteria.  With this
release, the problem is corrected.



Support of the VAX Language-Sensitive Editor (LSE)

Support of the VAX Language-Sensitive Editor (LSE)

Version 3.3 and later of CDD supports the VAX
Language-Sensitive Editor (LSE).  If the VAX


                        1-3



Release Notes

Release Notes


Language-Sensitive Editor is installed on your
system, you can use this feature to help write,
compile, and debug CDDL definitions.  The CDDL
Language-Sensitive Editor provides templates and
menus to walk you through CDDL options and syntax.
It is especially useful for users unfamiliar with
CDDL.

To invoke the Language-Sensitive Editor, type LSE at
the DCL prompt.  The following command, for example,
creates a file ADDRESS.CDDL and displays a CDDL
record definition template to guide you through the
process of describing a CDDL record:

$ LSE ADDRESS.CDDL

When LSE compiles your source definition, it expects
a file type of .CDDL.  The CDDL compiler now
recognizes both file types .CDDL and .DDL.



/DIAGNOSTICS Qualifier for CDDL Command

/DIAGNOSTICS Qualifier for CDDL Command

The /DIAGNOSTICS qualifier with the CDDL command
creates a diagnostics file that lists errors
occurring during compilation.  /DIAGNOSTICS is
designed for use from the LSE environment.
/DIAGNOSTICS lists errors in a file that has the
default name of your definition file and the
extension .DIA.  The diagnostic file is reserved for
use by DIGITAL.  LSE uses the diagnostic file to
display diagnostic messages and to position the
cursor on the line and column where a source error
exists.







                        1-4



                                       Release Notes

                                       Release Notes


You cannot use /DIAGNOSTICS with CDDL/RECOMPILE.

                                               ___

For complete information on using LSE, see the VAX
__________________ ______ ______ _____

Language-Sensitive Editor User's Guide.



DECreporter Support

DECreporter Support

If DECreporter is installed on your system, you can
use it to create reports using definitions stored in
the CDD.  You can use either DATATRIEVE or
DECreporter's Report Dictionary Management Utility
to manipulate dictionary objects.  With DATATRIEVE,
DECreporter lets you create reports using Rdb/VMS
and DBMS definitions in the CDD.

DECreporter supports two ways to define a report:

      o  A menu interface, which helps you navigate
         through the CDD to specify the report
         criteria.

      o  The DECreporter program interface, which
         lets you use DECreporter calls in a command
         file.

To run DECreporter, type REPORT at DCL level.  You
can type HELP REPORT for information on DECreporter
commands and qualifiers.



CDDL Alternative File Extension in CDD Version 3.3

CDDL Alternative File Extension in CDD Version 3.3
and Later

and Later

To support LSE, the CDDL compiler now recognizes the
definition file extension .CDDL as well as .DDL.




                        1-5



Release Notes

Release Notes


CDD Version 3.4 and VAX/VMS Version 4.4

CDD Version 3.4 and VAX/VMS Version 4.4

You can install CDD Version 3.4 only on a VAX/VMS
Version 4.4 or higher system.



Installing CDD on a Cluster

Installing CDD on a Cluster

If you are using CDD Version 3.4 on a VAX/VMS
Version 4.x cluster, you should install the main
dictionary file (CDD.DIC) on a device that is
accessible to the entire cluster.

You should also make sure that all system logical
names (including CDD$DICTIONARY, which is used to
identify dictionary files) translate in the same way
on each system in the cluster.  Otherwise, the same
subdictionary directory may point to several
different dictionary files, or you may receive a CDD
error that several subdictionary directories point
to the same subdictionary file.




















                        1-6



                                       Release Notes

                                       Release Notes


Underscore Preceding CDD_$TOP

Underscore Preceding CDD_$TOP

With CDD Version 3.1 and later, you can temporarily
define a logical name for CDD_$TOP.  (See Section
             ___ ______ ____ __________ ______ _____

8.3.1 of the VAX Common Data Dictionary User's Guide
for a description of the circumstances under which
you might define a logical name for CDD_$TOP.)

In path names displayed on the terminal, CDD places
an underscore before CDD_$TOP.  The name CDD_$TOP is
always translated at least once.  After the final
translation, CDD_$TOP will automatically be preceded
by an underscore (__CDD_$TOP).

If a logical name translates to an absolute path
name, then CDD_$TOP will be translated again.  For
example, CDD_$DEFAULT might translate to
CDD_$TOP.JONES.  Then CDD_$TOP is translated a final
time to __CDD_$TOP.



Using Multiple Versions of CDD Objects with

Using Multiple Versions of CDD Objects with
DATATRIEVE

DATATRIEVE

With CDD Versions 3.0 and later, you can create
multiple versions of dictionary objects.  If you are
using DATATRIEVE, however, you need DATATRIEVE
Version 3.x to access multiple versions of CDD
objects.  Earlier versions of DATATRIEVE do not
support multiple versions of dictionary objects.



Installing CDD with SYSPRV

Installing CDD with SYSPRV

If you use the INSTALL utility to install a known
image with the qualifier
/PRIVILEGED=(SYSPRV), you must install the
associated message file with the qualifier _/SHARED.


                        1-7



Release Notes

Release Notes


Otherwise, the image cannot access its own message
file.  For example, if you install DMU with SYSPRV,
you should install DMUEXC.EXE, DMU's message file,
with the qualifier /SHARED.



Path Names Pointing to Subdictionary Files

Path Names Pointing to Subdictionary Files

When you move a subdictionary file from one system
to another, make sure that the subdictionary's path
name on the new system is the same as it was on the
old system.  Because both DATATRIEVE and DBMS use
full path names by default to locate data
definitions, changing the path name of a
subdictionary will produce errors when DATATRIEVE or
DBMS tries to access definitions in that
subdictionary.

Currently, CDD does not check to ensure that
subdictionary path names remain unchanged.



The CDDL ALIGNED Clause

The CDDL ALIGNED Clause

Be careful when you use the CDDL ALIGNED clause.

o  You should not use the ALIGNED clause in template
   records.  When CDDL stores the template record,
   the position of an aligned field is fixed within
   the record and is not changed when the record is
   copied into another record definition.
   Therefore, the newly created field may not align
   properly in the new record definition.

o  Records created with the ALIGNED clause using
   previous versions of CDDL may not have aligned
   fields properly.  CDD Version 3.1 corrected this
   alignment problem.  However, if you recompile the


                        1-8



                                       Release Notes

                                       Release Notes


   records using the ALIGNED clause, data already
   stored will no longer match the recompiled data
   definition.




DMU Restrictions

DMU Restrictions

You should be aware of several restrictions in the
CDD Data Management Utility (DMU).



Copying and Renaming a Dictionary Object Protected

Copying and Renaming a Dictionary Object Protected
by a Password

by a Password

Cases may occur where you are granted UPDATE and
CONTROL privileges for an object only through a
password.  If this is true, you cannot copy any
version of another object with the same name as the
protected object to the directory containing the
protected object, because DMU COPY provides no way
to specify the protected object's password.

In a case where you are granted the UPDATE privilege
for an object only through a password, you cannot
rename another object as a new version of the
protected object, because DMU RENAME provides no way
to specify the protected object's password.



Using /STAGE with DMU RESTORE

Using /STAGE with DMU RESTORE

If you specify the /STAGE qualifier with the DMU
RESTORE command, all changes remain in virtual
memory until the restoration is completed, to assure
that either all or none of the changes are made.
Therefore, the size of the portion you back up is


                        1-9



Release Notes

Release Notes


limited by the amount of virtual memory.  By
contrast, /NOSTAGE (the default) frees virtual
memory in stages, as each directory is restored.

The DMU BACKUP and RESTORE commands should be used
to back up only portions of the dictionary
hierarchy.  Use the DCL BACKUP command to back up an
entire dictionary file.



Using a Wildcard with the DELETE/SUBDICTIONARY

Using a Wildcard with the DELETE/SUBDICTIONARY
Command

Command

With one DELETE/SUBDICTIONARY command you can delete
only 255 or fewer subdictionaries.


























                        1-10
